===================================================================================================
 The BLINKER environment variable
------------------------------------------------------------------------------
 At program start up the Blinker kernel checks the DOS environment for the
 BLINKER environment variable, which allows certain Blinker settings to be
 overridden at program run time. The name of this environment variable can be
 changed at link time with the BLINKER ENVIRONMENT NAME command. For more
 details refer to the BLINKER ENVIRONMENT NAME section of the online help.in
 Chapter 9. If the environment variable name is present, the variable is
 examined for the following settings:

 /CEnnn,nn   Amount of EMS to use for overlay cache
 /CXnnn,nn   Amount of XMS to use for overlay cache
 /DHn        Debug Handle
 /DI3        Debug Interrupt 3
 /DTnnnn     Dual Mode threshold in KB
 /EBnnnn     Extended memory block size in KB
 /ED-        Disable extender debugging
 /ED+        Enable extender debugging
 /EInnn      Extender IPX buffers count
 /EK-        Disable extender special keyboard handling
 /EK+        Enable extender special keyboard handling
 /ELnnnn     Extended memory limit in KB
 /ETnnnn     Extended Mode threshold in KB
 /HD-        Disable DPMI host support
 /HD+        Enable DPMI host support
 /HM-        Disable display of host messages
 /HM+        Enable display of host messages
 /HP-        Disable host passup of IRQ interrupts
 /HP+        Enable host passup of IRQ interrupts
 /HQ-        Disable QDPMI host support
 /HQ+        Enable QDPMI host support
 /HV-        Disable VCPI host support
 /HV+        Enable VCPI host support
 /HX-        Disable XMS host support
 /HX+        Enable XMS host support
 /LRnn       Reserve memory < 1 Mb for program use
 /OOnn       Overlay pool Operating size in KB
 /OP-        Disable use of EMS pageframe for overlays
 /OP+        Enable use of EMS pageframe for overlays
 /OU-        Disable use of XMS UMBs for overlays
 /OU+        Enable use of XMS UMBs for overlays
 /SD<path>   Directory for SWPRUNCMD() swap file
 /SE-        Disable use of EMS by SWPRUNCMD()
 /SE+        Enable use of EMS by SWPRUNCMD()
 /SU-        Disable use of UMBs by SWPRUNCMD()
 /SU+        Enable use of UMBs by SWPRUNCMD()
 /SX-        Disable use of XMS by SWPRUNCMD()
 /SX+        Enable use of XMS by SWPRUNCMD()
 /WS-        Disable detection of SoftICE/W
 /WS+        Enable detection of SoftICE/W

 The /CEnnn,nn setting is an override of the link time command BLINKER CACHE
 EMS nnn which controls the amount of EMS memory used by the overlay manager
 for overlay caching. For details of the usage of these values, see the
 command BLINKER CACHE EMS in the online help.

 The /CXnnn,nn setting is an override of the link time command BLINKER CACHE
 XMS nnn which controls the amount of XMS memory used by the overlay manager
 for overlay caching. For details of the usage of these values, see the
 command BLINKER CACHE XMS in the online help.

 The /DHn setting is an override of the link time Blinker command BLINKER
 DEBUG HANDLE n which controls the handle of the destination of debug output
 from Blinker. For details of the usage of this value, see the command
 BLINKER DEBUG HANDLE in the online help.

 The /DI3 setting enables the creation of a debug interrupt 3 instruction
 just before the Blinker kernel jumps to the first line of the main program.
 This setting should only be used while debugging. For more details see the
 debugging sections in the online help.

 The /DTnnnn setting is an override of the link time Blinker command BLINKER
 EXECUTABLE DUAL nnnn which controls whether a dual mode program runs in real
 or protected mode. This can also be used during testing to force the program
 to run in real mode by setting /DT20000 (or some suitably large figure). For
 details of the usage of this value, see the command BLINKER EXECUTABLE DUAL
 in the online help.

 The /EBnnnn setting is an override of the link time BLINKER EXTMEM BLOCK
 command, which is used to control the Blinker extender's memory allocation
 block size. For further details, see the BLINKER EXTMEM BLOCK command in the
 online help.

 The /EDc setting (where c=- is disabled and c=+ is enabled) controls the
 debugging mode of the Blinker extender. These settings enable and disable
 certain debugging messages provided by the extender, such as checking for
 aliasing of segments which are not locked or not present, and freeing of
 selectors using a free memory function call. It is advisable to test your
 programs running under a VCPI or XMS host (ie not DPMI) with this option
 enabled to check for these circumstances. The default is disabled.

 The /EInnn setting specifies the number of IPX ECB buffers allocated by the
 extender's IPX module. The default value is 32. For details, see the BLINKER
 EXECUTABLE IPX command in the online help.

 The /EKc setting (where c=- is disabled and c=+ is enabled) controls the
 keyboard handling of the Blinker extender. These settings enable and disable
 special handling of certain keyboard BIOS calls by the extender to prevent
 needless mode switching. When enabled, this option can increase the
 performance of serial communications routines. When disabled, this option
 may improve compatability with old TSRs which manipulate the keyboard. The
 default is disabled.

 The /ELnnnn setting is an override of the link time BLINKER EXTMEM LIMIT
 nnnn command, which is used to control the total amount of extended memory
 allocated by the Blinker extender. For details, see the BLINKER EXTMEM LIMIT
 command in the online help.

 The /ETnnnn setting is an override of the link time BLINKER EXECUTABLE
 EXTENDED nnnn command, which is used to control whether an extended mode
 program is able to run in the memory available. For details, see the BLINKER
 EXECUTABLE EXTENDED command in the online help.

 The /HDc setting (where c=- is disabled and c=+ is enabled) is an override
 of the link time BLINKER HOST DPMI command, which controls the usage of a
 DPMI host by the Blinker extender. For further details, see the BLINKER HOST
 DPMI command in the online help.

 The /HMc setting (where c=- is disabled and c=+ is enabled) is an override
 of the link time BLINKER HOST MESSAGES command, which controls the display
 of host messages by the Blinker extender. For further details, see the
 BLINKER HOST MESSAGES command in the online help.

 The /HPc setting (where c=- is disabled and c=+ is enabled) is an override
 of the link time BLINKER HOST PASSUP command, which controls the automatic
 pass up of IRQ interrupts from real mode to protected mode by the Blinker
 extender. This setting should only be necessary for debugging purposes when
 testing interrupt handlers, and is enabled by default. For further details,
 see the BLINKER HOST PASSUP command in the online help.

 The /HQc setting (where c=- is disabled and c=+ is enabled) is an override
 of the link time BLINKER HOST QDPMI command, which controls the usage of a
 QDPMI host by the Blinker extender. For further details, see the BLINKER
 HOST QDPMI command in the online help.

 The /HVc setting (where c=- is disabled and c=+ is enabled) is an override
 of the link time BLINKER HOST VCPI command, which controls the usage of a
 VCPI host by the Blinker extender. For further details, see the BLINKER HOST
 VCPI command in the online help.

 The /HXc setting (where c=- is disabled and c=+ is enabled) is an override
 of the link time BLINKER HOST XMS command, which controls the usage of an
 XMS host by the Blinker extender. For further details, see the BLINKER HOST
 XMS command in the online help.

 The /LRnnn setting is an override of the link time Blinker command BLINKER
 LOWMEM RESERVE nnn which controls the amount of conventional memoy reserved
 for program use, preventing Blinker's DOS extender from using it for other
 purposes. For further details,details of the usage of this value, see the
 command BLINKER LOWMEM RESERVE in the online help.

 The /OOnn setting is an override of the link time Blinker command BLINKER
 OVERLAY OPSIZE nn which controls the operating size of the Blinker overlay
 pool. For details of the usage of this value, see the command BLINKER
 OVERLAY OPSIZE in the online help.

 The /OPc setting (where c=- is disabled, and c=+ is enabled) is an override
 of the link time Blinker command BLINKER OVERLAY PAGEFRAME which controls
 the allocation of the overlay pool using the EMS (3.2+) pageframe. For
 details of the usage of this value, see the command BLINKER OVERLAY
 PAGEFRAME in the online help.

 The /OUc setting (where c=- is disabled, and c=+ is enabled) is an override
 of the link time Blinker command BLINKER OVERLAY UMB which controls the
 allocation of the overlay pool using XMS 2.0 upper memory blocks. For
 details of the usage of this value, see the command BLINKER OVERLAY UMB in
 the online help.

 Note: the Blinker overlay manager obtains control before the program begins
 execution, so the system resources controlled by the previous settings are
 allocated before the main program gets control.
 The BLINKER environment variable may also be used to alter the behaviour of
 Blinker's built in swap function (SWPRUNCMD()), using the following
 settings:

 The /SD<path> setting may be used to specify a directory path to be used by
 SWPRUNCMD() when saving the parent program's image to disk. This setting is
 an override of the `temporary directory' parameter passed to SWPRUNCMD()
 itself. For further details, see the function SWPRUNCMD() in the online
 help.

 The /SEc setting (where c=- is disabled, and c=+ is enabled) is an override
 of the swap function SWPUSEEMS(), which controls the usage of EMS memory by
 SWPRUNCMD() for saving the parent program's memory image. For further
 details, see the function SWPUSEEMS() in the online help.

 The /SUc setting (where c=- is disabled, and c=+ is enabled) is an override
 of the swap function SWPUSEUMB(), which controls the usage of UMBs by
 SWPRUNCMD() for relocating the resident portion of the swap function's
 kernel. For further details, see the function SWPUSEUMB() in the online
 help.

 The /SXc setting (where c=- is disabled, and c=+ is enabled) is an override
 of the swap function SWPUSEXMS(), which controls the usage of XMS memory by
 SWPRUNCMD() for saving the parent program's memory image. For further
 details, see the function SWPUSEXMS() in the online help.

 The /WSc setting (where c=- is disabled, and c=+ is enabled) enables or
 disables checking for the presence of the NuMega SoftICE/W debugger in
 protected mode running in a DOS box of Windows. This setting is enabled by
 default. For further details, see the section entitled `NuMega SoftICE/W
 debugger' in the `Special features' chapter of the manual and online help.

 The BLINKER environment variable can be used to alter settings quickly while
 testing an application, and to provide unique settings for individual
 workstations once the application is in production.
 Settings in the BLINKER environment variable should be separated by spaces,
 ie:

 SET BLINKER=/HM+ /ET2000

 This example enables the display of host messages by the Blinker extender
 and sets the extended memory threshold to 2000 Kb.

 The default environment variable name `BLINKER' can be changed with the use
 of the command BLINKER ENVIRONMENT NAME, which will avoid conflict with
 other Blinker linked programs that are present on the same computer.

 For example, you could change the name to `MYAPP', causing Blinker to ignore
 the `BLINKER' variable, and use `MYAPP' instead:

 SET MYAPP=/OP- /OO30 /CX128
===================================================================================================
===================================================================================================
CA-Clipper Real Mode Linker--BLINKER.EXE
 Features high-speed linking, dynamic overlaying, caching of overlay,
 compression of the symbol table, and "burning" the CLIPPER environment
 variable
------------------------------------------------------------------------------

 Blinker Commands

     Script file(s) are specified on the command line and default to an
     extension of .LNK.  They may be nested, and more than one may be used on
     the command line, for example:

     BLINKER @Defaults @Other LIB Mylib VERBOSE

     This command line instructs Blinker to read the script file DEFAULTS.LNK
     followed by the script file OTHER.LNK.  It also instructs Blinker to use
     the library MYLIB.LIB and to display a VERBOSE listing of the .OBJ files
     being processed.  The full names of the commands, or any unique
     abbreviation of the words which comprise the commands, may be used
     although it is recommended that at least three letters be used for
     clarity.  For example, the command BLINKER OVERLAY OPSIZE 40 can be
     abbreviated to BLI OVE OPS 40.

     Most Blinker commands may be specified in any order, at any point in the
     link script file.  Typically the first FILE statement should specify the
     .OBJ containing the main program procedure.

     # ...

     Indicates text as a script file comment.  Any line in the script file
     beginning with the character # is treated as a comment and is ignored by
     Blinker.  If the # ... character occurs within a line, the rest of the
     line is ignored.

     // ...

     Indicates text as a script file comment.  Any line in the script file
     containing the characters // is treated as a comment and is ignored by
     Blinker.  If the // ... characters occur within a line, the rest of the
     line is ignored.

     @<scriptname>

     Specify the name of a script file.  Blinker supports nested script files
     of any size to a depth of 5 levels.  The processing of nested script
     files is similar to a program function call.

     BEGINAREA

     Specifies the start of a dynamic overlay area to the linker.  Each
     BEGINAREA should have a corresponding ENDAREA to indicate the end of the
     overlay area.

     BLINKER CACHE EMS <nuMax[%]>
        [, <nuMinLeave[%]>]

     Specifies the amount of EMS (LIM version 4.0 and higher) memory to be
     used for the overlay cache.  Two numeric parameters are used to specify
     the amount of EMS memory to be allocated and the amount to be left for
     program use.  Both parameters may be specified as either a number of KB,
     or as a percentage of the total available EMS.

     BLINKER CACHE XMS <nuMax[%]>
        [, <nuMinLeave[%]>]

     Specifies the amount of XMS (version 2.0 and higher) memory to be used
     for the overlay cache.  Two numeric parameters are used to specify the
     amount of XMS memory to be allocated and the amount to be left for
     program use.  Both parameters may be specified as either a number of KB,
     or as a percentage of the total available XMS.

     BLINKER CLIPPER PAGE ON | OFF

     Enables/Disables automatic CA-Clipper 5.3 code paging.

     BLINKER ENVIRONMENT CLIPPER <cName>

     Changes the name of the CA-Clipper environment variable from the default
     setting of "CLIPPER" to any string of up to 16 characters, and thus
     avoids the remote site settings for the CLIPPER environment variable.

     BLINKER ENVIRONMENT NAME <cName>

     Specifies the name of the environment variable for Blinker runtime
     options.  By default, if the argument is not specified, the default
     setting is BLINKER.

     BLINKER ENVIRONMENT OVERRIDE

     Commands Blinker to allow the CA-Clipper environment variables set using
     the BLINKER EXECUTABLE CLIPPER command to be overridden at application
     run time by the settings of the CLIPPER environment variable.  When
     doing this, you may want to consider renaming your CLIPPER environment
     variable with the command BLINKER ENVIRONMENT CLIPPER.

     BLINKER EXECUTABLE CLIPPER <cEnvironmentstring>

     Burns default values for the CA-Clipper runtime environment variables
     into the executable file.  Those settings set using the BLINKER
     EXECUTABLE CLIPPER command take precedence over those set with the SET
     CLIPPER command.

     BLINKER EXECUTABLE NODELETE

     Creates .EXE regardless of unresolved externals, although the resulting
     .EXE is not guaranteed to operate correctly.

     BLINKER LINK EMS ON | OFF

     Controls whether or not EMS memory is used at link time by the virtual
     memory system within Blinker.

     BLINKER LINK PAGEFRAME ON | OFF

     Controls the use of the EMS pageframe by Blinker at link time by the
     virtual memory system within Blinker.

     BLINKER LINK XMS ON | OFF

     Controls whether or not XMS memory is used at link time by the virtual
     memory system within Blinker.

     BLINKER MESSAGE DUPLICATES

     Causes Blinker to generate the 1004 link-time warning message for all
     duplicate symbols within libraries encountered at link time.

     BLINKER MESSAGE NOBLINK

     Disables the blinking eyes which are displayed while Blinker is running.

     BLINKER MESSAGE NOWARNING

     Suppresses the display of Blinker link-time warning messages 1001 to
     1100.

     BLINKER MESSAGE WINK [LEFT]

     Enables single eye winking during linking.  If no parameter is entered,
     the right eye will wink (from Blinker.s point of view, i.e., from inside
     the screen looking out).  The parameter LEFT causes the left eye to
     wink.

     BLINKER OVERLAY OPSIZE <nuSize>

     Requests a size for the overlay pool at run time in KB.  It can be set
     to any value between 12KB and 128KB.  The default operating size is
     40KB.

     BLINKER OVERLAY PAGEFRAME ON | OFF

     Allows the overlay manager to utilize the expanded memory pageframe for
     the overlay pool (maximum size 64Kb), on machines equipped with LIM EMS
     (3.2 or higher) expanded memory boards or emulators.

     BLINKER OVERLAY THRESHOLD <nuLimit>

     Sets the threshold (limiar ou valor mnimo) size below which code 
     specified to be overlaid will be moved back to the root section of the program.

     BLINKER OVERLAY UMB ON | OFF

     Used in conjunction with a suitable XMS driver it allows the Blinker
     overlay manager to execute overlays in upper memory blocks above 640KB.

     BLINKER PROCEDURE DEPTH <nuDepth>

     Specifies maximum depth of CA-Clipper procedure nesting.  This depth is
     the number of procedure calls that are executed before a procedure
     return.

     DEFINE <symbol>[, <symbol> ...]

     Specifies symbols to be excluded at link time and points them to a dummy
     routine in the overlay manager.

     DEFLIB

     Uses default library search records to locate and link libraries which
     are specified within an object module.

     ECHO [ON | OFF |] [<cString>]

     ECHO ON <cString> turns on echoing of the script file to the screen,
     with the first line displayed being <cString> if it is specified.  ECHO
     OFF turns off echoing to the screen of the script file and ignores the
     rest of the line.

     ENDAREA

     Specifies the end of an overlay area to the linker, as described in the
     BEGINAREA section.

     EXTDICTIONARY

     Specifies that Blinker should use the extended dictionary that is
     appended to library files by some librarian utility programs.

     FILE [d:][path]<filename>
        [, [d:][path]<filename> ...]

     Specifies to the linker the names of one or more .OBJ files to be
     included in the output file at that point.

     LIBRARY [d:][path]<libname>
        [, [d:][path]<libname> ...]

     Specifies one or more program libraries required by the program.

     MAP [=[d:][path]<filename>] [S][,A]

     Requests a segment map of the executable.

     MIXCASE

     Causes Blinker to treat all publics and externals as case sensitive at
     link time, rather than converting them to UPPERCASE.

     MODULE <module> [,<module> ...]
        [FROM <libname>]

     Specifies placement of individual library modules regardless of whether
     the originating libraries or object modules are specified within an
     overlay area or not.

     MURPHY

     Causes the overlay manager to attempt to force any inadvertent overlay
     errors (programming errors) to manifest themselves during testing or
     debugging.

     NOBELL

     Suppresses the beep upon completion of link.

     NODEFLIB

     Ignores default library search records which are encountered within
     object modules.

     NOEXTDICTIONARY

     Disables processing of extended library dictionaries.

     NOTABLEOFCONTENTS

     Disables processing of library table of contents.

     OUTPUT [drive:][path]<filename>

     Specifies the name of the output executable file to be created by the
     linker.

     READONLY

     Specifies executable file will be set to read-only status.

     SEARCH [d:][path]<libname>
        [, [d:][path]<libname> ...]

     Prioritizes all symbols in the specified libraries.

     SECTION INTO <ovlname>
        [FILE [d:][path]<filename>
        [, [d:][path]<filename>...] ]

     Specifies files to be placed in an external overlay.

     STACK <nuSize>

     Specifies to Blinker in HEXADECIMAL the stack size in bytes required by
     the program .EXE file.

     UPPERCASE

     Specifies to the linker that all symbols should be converted to
     uppercase before being added to the symbol table.

     VERBOSE [0 | 1 | 2]

     Displays status information during linking.

     WORKFILE [d:][path]<filename>

     Specifies drive, path, and file name of the temporary WORKFILE to use at
     link time if one is required.

 Linker Function

     nuValue := BLIVERNUM()

     Returns the Blinker version number as an integer containing the version
     number of Blinker used to link the program.
*
===================================================================================================
pra finalizar vai a a gama de parametros que achei para o blinker... 
mas ninguem sabe ao certo o que faz todos eles. 
J USEI VARIAS COMBINACOES E NADA. 

#------------------------Exemplo 1 Simples ----------------------------- 
BLINKER EXECUTABLE CLIPPER F220;SWAPPATHC:\TEMP; 
BLINKER EXECUTABLE COMPRESS 1 
BLI EXE EXT # Remove for Real mode 
BLINKER INCREMENTAL OFF # To improve Memory(0) and speed 

------------------------Exemplo 2 ------------------------------------- 
Blinker Cache EMS 50%,50% 
Blinker Cache XMS 50%,50% 
Blinker Link EMS ON 
BLINKER EXECUTABLE CLIPPER F220;SWAPPATHC:\TEMP; 
Blinker Link XMS ON 
Blinker Exec Exte 
BLINKER EXECUTABLE COMPRESS 1 
Blinker Memo Pack 60 
Blinker Incr Pad 256 
Blinker Over Page On 
Blinker Over Opsi 60 

------------------------Exemplo 3 ------------------------------------- 
BLINKER INCREMENTAL OFF 
BLINKER CLIPPER PAGE OFF 
BLINKER link XMS ON 
BLINKER EXECUTABLE EXTENDED 2048 
BLINKER HOST MESSAGE ON 
BLINKER HOST DPMI ON 
BLINKER HOST VCPI ON 
BLINKER HOST XMS ON 
BLINKER PROCEDURE DEPTH 70 
BLINKER EXECUTABLE COMPRESS 1 
blinker executable nodelete 
stack 7068 
map 
nobell 

------------------------Exemplo 4 ------------------------------------- 
BLINKER EXECUTABLE EXTENDED 
BLINKER EXECUTABLE ALIGN 64 
BLINKER INCREMENTAL OFF 
BLINKER EXECUTABLE NODELETE 
BLINKER EXECUTABLE CLIPPER /F:255 /DYNF:8 /SWAPK:65535 /SWAPPATH:'' /TEMPPATH:'' 
NOBELL 
STACK 7168 
BLINKER INCREMENTAL OFF 
BLINKER OVERLAY FIXED 
BLINKER OVERLAY UMB ON 
BLINKER OVERLAY PAGEFRAME ON 
BLINKER CACHE EMS 256,0% 
BLINKER CACHE XMS 256,0% 
BLINKER OVERLAY OPSIZE 40 
BLINKER EXECUTABLE CLIPPER F200 
------------------------Exemplo 5 ------------------------------------- 
BLINKER INCREMENTAL OFF 
BLINKER EXECUTABLE CLIPPER F250 
BLINKER PROCEDURE DEPTH 140 
BLINKER EXECUTABLE NODELETE 
BLINKER EXECUTABLE COMPRESS 1 
BLINKER EXECUTABLE EXTENDED 
stack 7068 
MAP S,A 
#------------------------Exemplo 6 ------------------------------------- 

BLINKER OVERLAY FIXED         # Use a fixed overlay area instead of the free pool 
BLINKER OVERLAY OPSIZE 60     # Allocate 60k to the overlay pool 
BLINKER INCREMENTAL OFF       # Perform a full link 
BLINKER OVERLAY PAGEFRAME ON  # Use expanded ram for overlay pool to save memory 
BLINKER OVERLAY THRESHOLD 256 # Use these commands only if using Blinker 2.0 and above 
BLINKER CACHE XMS 512, 25% 
BLINKER CACHE EMS 128, 50% 
BLINKER EXECUTABLE EXTENDED   # Usa memoria extendida 
BLINKER EXECUTABLE NODELETE   # Cria exe apesar dos "unresolved external" 
#------------------------Exemplo 7 ------------------------------------- 
BLINKER INCREMENTAL OFF 
BLINKER MEMORY CLEAR 1 
BLINKER CACHE XMS 8192, 25% 
BLINKER OVERLAY OPSIZE 1 
BLINKER OVERLAY UMB ON 
BLINKER OVERLAY THRESHOLD 64 
BLINKER EXECUTABLE EXTENDED 8192 // 4096 //8192 
BLINKER EXECUTABLE ALIGNMENT 64 
BLINKER EXTMEM BLOCK 512 
BLINKER EXTMEM LIMIT 8192 //4096 //8192 
BLINKER LOWMEM RESERVE 64 
BLINKER OVERLAY PAGEFRAME ON 
BLINKER HOST QDPMI ON 
BLINKER HOST DPMI ON 
BLINKER HOST VCPI ON 
BLINKER HOST XMS ON 
#------------------------Exemplo 8 ------------------------------------- 
# uso de overlays 
BLINKER OVERLAY FIXED 
BLINKER OVERLAY OPSIZE 60        # tamanho del overlay 60k 
BLINKER INCREMENTAL OFF          # linkado completo OFF /o no ON 
BLINKER OVERLAY PAGEFRAME ON     # uso de la memoria expandida para los overlays 
BLINKER OVERLAY THRESHOLD 256    # tamanho ms pequea para un overlay 
BLINKER CACHE XMS 512, 25% 
BLINKER CACHE EMS 128, 50% 

#------------------------Exemplo 9 ------------------------------------- 

Blinker Exec Clipper //BadCache //Dynf:8 //F:254 //Noidle (No use mais Set Clipper no Autoexec.bat) 
Blinker Exec Comp 2 
Blinker Host Mess Off 
Blinker Exec Exte 
Search BlxRatex 
Search BlxClp53 
Blinker Incr Pad 128 
Blinker Memory Pack 2 
Blinker Over Page On 
Blinker Over Opsi 60 
===================================================================================================
